Integrated mobile device

ABSTRACT

Provided are a system and method of interacting with a vehicle or a home control system. A context associated with a user input is obtained in relation to the vehicle or the home control system. An instruction based on the user input and the context is generated. The instruction is transmitted to the vehicle or the home control system to generate control or indication in connection with one of a component and a function of the vehicle or the home control system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is the U.S. National Phase of International PatentApplication No. PCT/US2014/031038, filed on 18 Mar. 2014, which claimsbenefit of U.S. Provisional Patent Application No. 61/852,524 filed onMar. 18, 2013, the contents of which are incorporated herein byreference in their entirety.

BACKGROUND

Field

The present application relates generally to mobile devices. Morespecifically, the present application is directed to a system and methodof providing contextualized display and control functionality.

Brief Discussion of Related Art

Mobile devices have become ubiquitous in society for variousapplications, such as computing, telecommunications, music, and otherapplications. Many of the foregoing and other applications have beenintegrated into smart devices (e.g., iPads, smartphones), which cangenerally interconnect to other devices using protocols such asBluetooth, NFC, Wi-Fi, 4G, as well as others, to provide richerfunctionality and worldwide interconnectivity.

Smart wearable devices have recently hit the marketplace and havereceived considerable attention. Smart wearable devices can includewatches, fitness bands, and eyewear, just to mention a few smartwearable devices. These and other smart wearable devices integrate(e.g., using Bluetooth and/or other protocols) with mobile devices (e.g.smartphones) to provide users with computing and display functionalityfor data collected by, or otherwise available on, the smart wearabledevices, enhancing user experience.

Moreover, new technologies are being developed to integrate mobiledevices into vehicle-related systems. Examples of such integrationinclude interconnectivity of smartphones (e.g., using Bluetooth and/orother protocols) with vehicle sound systems, which provide versatilityin streaming music, making/receiving telephone calls, as well as a hostof other applications. Some of these integrations not only provideefficiency and desirability but also facilitate safety, such as theability to make/receive telephone calls or generate/receive instantmessages hands free, just to mention a few.

The marketplace is heading in the direction of integration of mobiledevices with the functionality of other systems (e.g., vehicle-relatedsystems), providing new and/or improved functionality and applications,resulting in new and/or improved user freedoms in the collection,processing, display, control and communication of content.

Vehicle-related systems have seen an increase both in safety andtechnology, including new and improved functionality as well theintegration with mobile devices, such as smartphones. Today, usersdesire access to applications and content in their vehicles and furtherdesire to have personalized in-vehicle experience. Of course withimproved vehicle-mobile device integration, a major concern is thesafety in vehicle operation because of user (driver) cognitivedistraction. Another major concern is content security associated withmultiple integrated systems/devices. Strong user demand for applicationsand content in the vehicle continue to fuel these pressures, whichremain unabated.

Accordingly, it is desirable to manage interaction and integrationbetween the user, vehicle and mobile device, and other systems, in orderto deliver applications and content to the user that providepersonalized and contextualized display and control functionality, whichare secure and address the safety concerns.

SUMMARY

The present application is directed to a system and methods for theintegration of an integrated mobile device with a connectable vehicle(s)and a service provider(s). The system and methods provide for theselection and seamless integration of context associated with theintegrated mobile device in relation to the connectable vehicle withuser data and service provider data. Moreover, the system and methodsprovide control and display functionality based on the context selectionand various other data as described herein in greater detail.

Similarly, the application is also directed to a system and methods forthe integration of an integrated mobile device with a home controlsystem(s) and a service provider(s). The system and methods provide forthe selection and seamless integration of context associated with theintegrated mobile device in relation to the home control system withuser data and service provider data. Moreover, the system and methodsprovide control and display functionality based on the context selectionand various other data.

In accordance with an embodiment or aspect, a method of interacting witha vehicle is disclosed. The method includes obtaining a contextassociated with a user input in relation to the vehicle. An instructionbased on the user input and the context is generated. The instruction isthen transmitted to the vehicle to generate control or indication inconnection with one of a component and a function of the vehicle.

In accordance with another embodiment or aspect, a system to interactwith a vehicle is disclosed. The system includes a processing device anda memory. The memory device stores instructions that, when executed bythe processing device, cause the processing device to perform thefollowing operations. The operations include obtaining a contextassociated with a user input in relation to the vehicle, generating aninstruction based on the user input and the context, and transmittingthe instruction to the vehicle to generate control or indication inconnection with one of a component and a function of the vehicle.

In accordance with a further embodiment or aspect, a method ofinteracting with a home control system is disclosed. The method includesobtaining a context associated with a user input in relation to the homecontrol system. An instruction based on the user input and the contextis generated. The instruction is then transmitted to the home controlsystem to generate control or indication in connection with one of acomponent and a function of the home control system.

In accordance with yet another embodiment or aspect, a system tointeract with a home control system is disclosed. The system includes aprocessing device and a memory. The memory device stores instructionsthat, when executed by the processing device, cause the processingdevice to perform the following operations. The operations includeobtaining a context associated with a user input in relation to the homecontrol system, generating an instruction based on the user input andthe context, and transmitting the instruction to the home control systemto generate control or indication in connection with one of a componentand a function of the home control system.

These and other purposes, goals and advantages of the presentapplication will become apparent from the following detailed descriptionread in connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments or aspects are illustrated by way of example and notlimitation in the figures of the accompanying drawings in which:

FIG. 1 illustrates an example system that, among other things, providesintegration and communication of an integrated mobile device with aconnectable vehicle and a service provider, and provides contextualizedcontrol and display functionality in connection with the connectablevehicle;

FIG. 1A illustrates an example block diagram of example connectablevehicle of FIG. 1 that includes one or more direct sensors and one ormore network sensors;

FIG. 2 illustrates a block diagram of example vehicle sub-systems in theconnectable vehicle of FIG. 1;

FIG. 3 illustrates a block diagram of an example integrated mobiledevice of FIG. 1;

FIG. 4 illustrates a block diagram of example security credentialsformed by the connectable vehicle or by the service provider forconducting example communications in the communication system of FIG. 1;

FIG. 5 illustrates a block diagram of example security credentialsformed by the integrated mobile device for conducting examplecommunications in the communication system of FIG. 1;

FIG. 6 is a flowchart that illustrates an example method of formingsecurity credentials in accordance with FIG. 4 to conduct examplecommunications in the communication system of FIG. 1;

FIG. 7 is a flowchart that illustrates an example method of formingsecurity credentials in accordance with FIG. 5 to conduct examplecommunications in the communication system of FIG. 1;

FIG. 8 is a flowchart that illustrates an example method of providingcontext-based control associated with the connectable vehicle of FIG. 1;

FIG. 9 is a flowchart that illustrates an example method of providingcontext-based informational indication associated with the connectablevehicle of FIG. 1;

FIG. 10 is a block diagram that illustrates generation of an examplesystem-based initiation indicator based on anomaly detection as anexample input to the context-based control of the connectable vehicle ofFIG. 1 according to the method of FIG. 8, or as an example input to thecontext-based informational indication associated with the connectablevehicle of FIG. 1 according to method FIG. 9;

FIG. 11 is a flowchart that illustrates an example method of providingan example context based on breath sample and vehicle location tocontrol the connectable vehicle of FIG. 1 according to FIG. 8, or toprovide informational indication associated with the connectable vehicleof FIG. 1 according to FIG. 9; and

FIG. 12 is a block diagram of an illustrative embodiment of a generalcomputer system.

DETAILED DESCRIPTION

A system and method of providing contextualized information shaping fordisplay and control functionality are disclosed herein. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide a thorough understanding of exampleembodiments or aspects. It will be evident, however, to one skilled inthe art, that an example embodiment may be practiced without all of thedisclosed specific details.

FIG. 1 illustrates an example system 100. The example system 100provides integration of an integrated mobile device (e.g., smartwearable device) 104 with one or more connectable vehicles 106 and oneor more mobile computing devices 120 (as well as other systems) todeliver applications/content to the user, which can provide informationshaping and associated contextualized display and control functionalityin connection with the connectable vehicles 106 and service providers122.

In a vehicle-based implementations, context is defined by one or morefactors including a physical location of the integrated mobile device104 in relation to the connectable vehicle 106, authentication state ofthe user, physical activity of the user as determined (or accessible) bythe integrated mobile device 104 and/or other systems of the connectablevehicle 106, state of the service provider 122 in relation to theconnectable vehicle 106 and/or the user. Context can further be definedby one or more other factors including a physical location of theconnectable vehicle 106, state of the vehicle and/or one or moresub-systems in relation to the above-mentioned user-related and serviceprovider-related factors, as well as one or more other informationand/or data elements.

In a home-based implementations, context is defined by one or morefactors including a physical location of the integrated mobile device104 in relation to the home control system 126, authentication state ofthe user, physical activity of the user as determined (or accessible) bythe integrated mobile device 104, state of the service provider 122 inrelation to the home control system 126 and/or the user. Context canfurther be defined by one or more other factors including a physicallocation of the home control system 126, state of the home controlsystem, one or more sub-systems, or components therefor, in relation tothe above-mentioned user-related and service provider-related factors,as well as one or more other information and/or data elements.

The example system 100 includes a communication network 102, anintegrated mobile device 104 (e.g., smart wearable device as describedbelow), a connectable vehicle 106, a mobile computing device (e.g.,smartphone) 120 and a service provide device 122. In some embodiments,the system 100 can include a plurality of connectable vehicles 106 and aplurality of service provides 122. In some embodiments, the system 100can also include one or more home control systems 126, as well as one ormore other vehicles 128. The communication network 102 enablescommunication among the integrated mobile device 104, mobile device 120,connectable vehicles 106 and service providing systems 122. In variousembodiments, the network 102 can also enable communication to/from homecontrol systems 126 and other vehicles 128.

The communication network 102 can include one or more of long haultransport network (e.g., gigabit Ethernet network, Asynchronous TransferMode (ATM) network, and frame relay network), wireless network (e.g.,satellite network, Wi-Fi network, Bluetooth network, cellular network,or another wireless network), other public or private networks, or anycombination thereof. In addition, the communication network 102 can alsoinclude networks such as vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), commonly referred to as V2X networksthat provide connectivity amongst vehicles as well as connectivityto/from infrastructure. The foregoing is not exhaustive and alternate oradditional communication networks can be employed to interconnect theintegrated mobile device(s) 104, mobile computing device(s) 120,connectable vehicle(s) 106 and service providing system(s) 122, as wellas home control system(s) 126 and other vehicles 128.

The communication network 102 can include one or more of a wide areanetwork (WAN), local area network (LAN), virtual private network (VPN),peer-to-peer (P2P) network, as well as any other public or privatenetwork, or any combination thereof. Other conventional or yet to bedeveloped communications networks can form at least a part of thecommunication network 102. At least a portion of the transmission overthe communication network 102 can be accomplished, for example, viaTransfer Control Protocol/Internet Protocol (TCP/IP), User DatagramProtocol (UDP)/IP, or any combination of conventional protocols or yetto be developed protocols.

The integrated mobile device 104 can be a smart wearable device, such asbracelet or a watch that the user can wear around the user's wrist. Theintegrated mobile device 104 can also be any other type of smartwearable device, such as pendant, broach, eyeglasses, as well as anyother smart wearable device that currently exists or is yet to bedeveloped. The integrated mobile device 104 is configured to communicatewith other systems and devices illustrated in FIG. 1, among others,whether directly and/or using one or more networks, such as networks102, 108, to provide in a secure manner contextualized display andcontrol functionality. The components and their operation of theintegrated mobile device 104 are described in greater detail below withreference to FIG. 3. Mechanisms to provide secure communications, whichcan be used to provide user-to-integrated mobile device anduser-to-vehicle authorization for contextualized display and controlfunctionality, are described in greater detail below with reference toFIGS. 4 and 5. Contextualized display and control functionality aredescribed in greater detail below with reference to FIGS. 8-11.

The connectable vehicle 106 is generally any vehicle (e.g., car, truck,bus, motorcycle, or any other machine that can transport people and/orthings) that is configured to communicate with other systems and devicesillustrated in FIG. 1, among others, whether directly and/or using oneor more networks, such as networks 102, 108, to provide and/or deliverin a secure manner contextualized display and control functionality.

The connectable vehicle 106 includes a vehicle network(s) 108,direct-interface tag(s), sensor(s), beacon(s) 110 (referenced as directsensors or D_(N)), external network interface(s) 112, network-interfacedsensor(s) 114 (referenced as network sensors of S_(N)),vehicle-subsystems 116 and secure storage database system 118. Thevehicle network(s) 108 interconnects external network interface(s) 112,network sensors 114, and the secure storage database system 118.

The vehicle network 108 is generally any vehicle-based communicationnetwork or communication bus used to interconnect various vehiclefunction-related devices, sensors and subsystems. Examples of suchnetworks include Controller Area Network (CAN), Domestic Digital Bus(D2B), Byteflight, FlexRay, DC-BUS, IDB-1394, J1850, LIN, MOST, Wi-Fi,Bluetooth. One or more of such networks are generally used tointerconnect sub-systems like the Engine Control Unit (ECU), theTransmission Control Unit (TCU), the Anti-lock Braking System (ABS) andbody control module (BCM) and other diverse devices, sensors andsub-systems.

The direct sensors 110 can include tags, sensors, and beacons. Thedirect sensors are configured to communicate with the integrated mobiledevice 104 using one or more communication protocols (e.g., RFID, NFC,Bluetooth, Wi-Fi, FM and/or other communication protocols). The directsensors 110 have direct network connections to the integrated mobiledevice 104. The network sensors 114 can similarly include tags, sensors,and beacons, and are configured to communicate with the integratedmobile device 104 primarily over vehicle network(s) 108 using one ormore communication protocols, such as RFID, NFC, CAN, D2B, Bluetooth,Wi-Fi, FM and/or other communication protocols. Moreover, networksensors 114 are connected to the vehicle network(s) 108 to facilitatecommunications to the vehicle sub-systems 116 and database 118 of theconnectable vehicle 106, using one or more network communicationprotocols.

Example positioning of the direct sensors 110, the network sensors 114and the integrated mobile device 104 is illustrated in FIG. 1A. A directsensor 110 (e.g., a Bluetooth or NFC beacon) can be associated directlywith (and positioned proximately to) a component of the connectablevehicle 106 in connection with which the sensor is to determine ameasurement value and to provide the measurement value to the integratedmobile device 104 over a direct or bus connection, for example. As anexample, a direct sensor 110 can be associated with a particular tire asshown in FIG. 1A to provide tire pressure to the integrated mobiledevice 104 when the integrated mobile device 104 is in proximity to thetire. Similarly, other direct sensors 110 can provide measurements(e.g., oil pressure) in connection with other vehicle components (e.g.,engine).

Network sensors 114 can be used to determine positioning of theintegrated mobile device 104 in relation to components of theconnectable vehicle. For example, a network sensor 114 can determineposition of the integrated mobile device 104 in relation to a component(e.g., window/roof/sunroof controls, infotainment controls, seatcontrols, heating and cooling controls, or lighting controls, etc.) ofthe connectable vehicle 106. As another example, one or more of thenetwork sensors 114 can also triangulate a position and/or proximity ofthe integrated mobile device 104 in relation to a particular componentof the connectable vehicle 106, and can provide the positioning (and/orcomponent) to the integrated mobile device 104. It should be noted thatvarious types of data can be communicated to the integrated mobiledevice 104 via direct sensors 110, network sensors 114, and vehiclenetwork(s) 108, including vehicle-based data, metadata, telemetry data,data from various vehicle sub-systems and systems, user authenticationdata, vehicle control and information data, as well as any otheraccessible data not enumerated herein.

The external network interface(s) 112 provide the ability for theconnectable vehicle 106 (including its various sub-systems 116) tocommunicate with one or more mobile computing devices (e.g.,smartphones) 120, one or more service providers 122, one or more homecontrol systems 126, as well as to one or more other vehicles 128.

The vehicle sub-system(s) 116 provide functionality to control variouscomponents of the connectable vehicle 106, such as security, lighting,navigation, infotainment, vehicle control, driver assist, telematics,and as well as a variety of other components, including Engine ControlUnit (ECU), the Transmission Control Unit (TCU), the Anti-lock BrakingSystem (ABS), body control module (BCM) and other diverse devices,sensors and sub-systems. Example vehicle sub-systems 116 are illustratedin FIG. 2. Various vehicle components, modules, systems and sub-systemscan be interconnected by a bus (e.g., bus 202 in FIG. 2) and/or vehiclenetwork(s) 108.

The secure storage database 118 is configured to maintain securelyvarious security credentials (e.g., certificates) for establishing andmaintaining communication sessions, as well as user and serviceprovider(s) identities and associations, among the integrated mobiledevice 104, connectable vehicle 106 and service provider 122. Other datacan be maintained in the secure storage database 118, as described ingreater detail below.

The mobile computing device 120 can be any conventional smartphone,tablet or other computing device. The mobile device 120 includeswireless or wired access technology (e.g., Wi-Fi, cellular, Bluetooth,USB Direct, etc.) and can communicate with the integrated mobile device104 and the connectable vehicle 106.

In the vehicle-based implementations, the service provider(s) 122 istypically related to the connectable vehicle(s) 106 and its users. Forexample, a BMW service provider 122 is related to a BMW connectablevehicle 106. It is noted, however, that various other service providersthat are not related to the connectable vehicle 106 can be implementedin the system 100. Service providers 122 typically provide a range ofservices to the users of integrated mobile device 104 and/or users ofthe connectable vehicle 106. Such services include, but are not limitedto, running remote applications on the integrated mobile device 104 andthe connectable vehicle(s) 106, including its systems and sub-systems.Examples include vehicle maintenance monitoring services, weatherassistance services, surveillance services, shopping services, externalinformation referencing services, and a host of other types of services.

In the home-based implementations, the service provider(s) 122 istypically related to the home control system(s) 126 and its users. Forexample, an ADT service provider is related to an ADT home controlsystem 126. As another example, an appliance service provider 122 (e.g.,a sub-zero service provider) is related to an appliance (e.g., sub-zerorefrigerator), which may be a component of the ADT home control system126 or a sub-system of the home control system 126. It is noted,however, that various other service providers that are not related tohome control system 126 can be implemented in the system 100. Serviceproviders 122 typically provide a range of services to the users ofintegrated mobile device 104 and/or users of the home control systems126. Such services include, but are not limited to, running remoteapplications on integrated mobile device 104 and home control system(s)126, including various sub-systems and components. Examples includesub-system and/or component (appliances) maintenance and/or monitoringservices, weather assistance services, surveillance services, shoppingservices, external information referencing services, and a host of othertypes of services.

The integrated mobile device 104 in a similar fashion can also provideand/or deliver in a secure manner contextualized display and controlfunctionality with regard to one or more home control systems 126 aswell as one or more other vehicles 128. In the home-basedimplementations, the integrated mobile device 104 can be a remotecontroller to a home security system reachable via communication network102. In addition, the integrated mobile device 104 can also display astatus of the home control system, can arm/disarm the home controlsystem, and can relay to a user a status of various home-control sensorsand systems. When doing so, the integrated mobile device 104 can utilizecontext-based control and display functionality as described withreference to FIGS. 8 and 9, and can further use secure communications asdescribed with reference to FIGS. 5-7.

FIG. 1A illustrates a block diagram of example connectable vehicle 106that includes one or more direct sensors 110 and one or more networksensors 114.

As illustrated in FIG. 1A, an example direct sensor 110 can beassociated with a particular tire 130 to provide tire pressure to theintegrated mobile device 104 when the integrated mobile device 104 is inproximity to the tire. Similarly, another example direct sensor 110 canprovide an oil pressure measurement in connection with the engine 132 tothe integrated mobile device 104. Other direct sensors 110 can beprovided in associated with particulars components of the connectablevehicle 106. Direct sensors 110 are connected to integrated mobiledevice 104 over a direct network connection. They can also assistintegrated mobile device 104 in determining its location in relation toother components of the connectable vehicle 106.

Network sensors 114 as well as direct sensors 110 can be used todetermine position of the integrated mobile device 104 in relation tocomponents of the connectable vehicle. For example, a network sensor 114can determine position of the integrated mobile device 104 in relationto a sunroof component 134. As another example, a network sensor 114 candetermine position of the integrated mobile device 104 in relation toseat component 136 of the connectable vehicle 106. Moreover, one or moreof the network sensors 114 can also triangulate a position and/orproximity of the integrated mobile device 104 in relation to aparticular component of the connectable vehicle 106, and can provide thepositioning (and/or component) to the integrated mobile device 104.Direct sensors 110 and network sensors 114 provide a diverse sensoryenvironment to the integrated mobile device 104, which can assist incontext generation as will be described herein.

In the home-based implementations, one or more direct sensors 110 andone or more network sensors 114 can be associated with particularcomponents of the home control system 126. For example, a direct sensor110 or network sensor 114 can be associated with a refrigerator (orthermostat) component to provide internal temperature in therefrigerator/freezer (or the home). As another example, a direct sensor110 or network sensor 114 can be associated with a component of the homecontrol system (e.g., outside door lock) and can relay to a user astatus of such component (e.g., locked). In similar fashion, the directsensors 110 and the network sensors 112 can be used to determineposition of the integrated mobile device 104 in relation to componentsof the home control system 126, which can similarly assist in contextgeneration.

FIG. 2 illustrates a block diagram of example vehicle sub-systems 116 inthe connectable vehicle 106 of the communication system 100. The vehiclesub-systems 116 can include a vehicle communication bus 202 thatinterconnects a security sub-system 204, advanced driver assistsub-system (ADAS) 206, infotainment sub-system 208, vehicle controlsub-system 210, lighting control sub-system 212, telematicscommunication sub-system, as well as one or more other sub-systemsand/or electronic components in the connectable vehicle 106. Vehicleinterface 218 interconnects the sub-systems 204-216 to the vehiclenetwork(s) 108 illustrated in FIG. 1, providing communication to othercomponents of the connectable vehicle 106 and external devices, such asthe integrated mobile device 104 via vehicle network(s) 108 and externalnetwork interface(s) 112. Examples of the vehicle communication bus 202include but are not limited to Controller Area Network (CAN), DomesticDigital Bus (D2B), Byteflight, FlexRay, DC-BUS, IDB-1394, J1850, LIN,MOST, Wi-Fi, Bluetooth, as well as any other deployed or yet to bedeveloped bus.

FIG. 3 illustrates a block diagram of an example integrated mobiledevice 104 in the communication system 100.

The integrated mobile device 104 is configured provide personalized andinformation shaping, rendering and associated contextualized display andcontrol functionality with regard to the connectable vehicle 106 (and/orhome control system 126), among other functionalities, which can providevarious technological improvements and address various safety concerns.

The integrated mobile device 104 includes a processor 302, memory 304,secure storage device 306, input devices 308, processing devices 326,output devices 336, and communication interfaces 348. The processor 302is interconnected to the storage device 306, input devices 308,processing devices 326 and communication interfaces 348 in order toreceive input, process input, display output, and communicate with otherdevices and/or systems of the communication system 100.

The processor 302 can execute the methods, functions or other logic asdescribed herein. The memory 304 and/or storage database 306 includeinstructions (e.g., software) that embody one or more of the methods,functions or other logic as described herein. The instructions mayreside completely, or at least partially, within the memory 304, securestorage 306 and/or within the processor 302 during execution by theprocessor 302 of integrated mobile device 104. The processor 302, memory304, and storage 306 can also include computer-readable media to storeinstructions.

The storage device 306 stores various data and information describedherein to facilitate the methods, functions and/or other logic asdescribed in this disclosure. For example, the storage device 306 canstore security credentials as described below with reference to FIGS. 4and 5.

The input devices 308 receive various data and information describedherein to facilitate the methods, functions and/or other logic asdescribed in this disclosure. The input devices 308 include amulti-function button device(s) 310, a touch input device(s) 312, anaccelerometer device(s) 314, a biometric device(s) 316, air qualitydetection device(s) 318, a position device(s) 320, audio capturedevice(s) 322, and video capture device(s) 324. The foregoing inputdevices 308 enable the user 401, 501 in FIGS. 4, 5 to provide differenttypes of input, as well as to select and/or actuate variousfunctionality, methods, functions and/or other logic as described hereinbased the input.

The multi-function button device(s) 310 can include various buttons orswitches that can be depressed, toggled or otherwise actuated by a userto receive various inputs from the user 401, 501. The touch inputdevice(s) 312 can include one or more touch devices (e.g., touchscreens)that can receive various inputs from a user. The accelerometer device(s)314 can provide motion data, while the position device(s) 320 canprovide position data, which are associated with the integrated mobiledevice 104.

The biometric device (316) can include various biometric devices toreceive biometric input from of the user, such as, for examplefingerprint/palm-print device, iris scanning device,heart-rate/pulse-rate measurement device, breathalyzer device,electrocardiogram device (ECG), electroencephalogram (EEG), as well asother biometric devices. The air quality detection device 318detects/measures quality of air, such as, for example, air temperature,velocity and humidity, carbon dioxide (CO2), carbon monoxide (CO), aswell any other detection or measurement.

The audio capture device(s) 322 can include one or more microphonesand/or other capture audio devices to receive audio input, while thevideo capture device(s) 324 can include one or more cameras and/or othervideo capture devices to receive video input (e.g., streaming video)and/or still image input (e.g., photograph(s)). It is noted that thelist of input device is not exhaustive, and one or more other inputdevices can be provided to receive various input data and informationdescribed herein to facilitate the methods, functions and/or other logicas described in this disclosure.

The processing devices 326 can be dedicated to performing certainspecific tasks, offloading these tasks from the processor 302. Theprocessing devices 326 include audio processing device 328, videoprocessing device 330 and biometric processing device 334. The audioprocessing device 328 receives input using the audio capture device(s)322 and process the input with voice recognition, such as toauthenticate the user 401, 501. The video processing device 328 receivesinput using the video capture device(s) 324 and process the input withimage/object recognition, such as to authenticate the user 401, 501 orto determine an object (and associated position) in connection with theconnectable vehicle 106 or the home control system 126, assisting withthe determination of context. Other dedicated processing devices can beprovided.

The output devices 336 output various data, indications and informationdescribed herein to facilitate the methods, functions and/or other logicas described in this disclosure. The output devices 336 includedisplay(s) 338, actuation device(s) 340, light emitting device(s) 342,speaker(s) 344 and projection device(s) 346. The display(s) 338 caninclude one or more displays, such as liquid crystal displays (LCDs) orother display technologies. The light emitting device(s) 342 can includea variety of LEDs. The speaker(s) 344 can be any one or more speakers ofvarious technologies to produce audible sounds. The projection device(s)346 can be one or more projectors to project certain data, information,or video onto a screen or other surface. Other output devices can beprovided. For example, various colors or brightness levels of the LED(s)342 may indicate various conditions associated with the connectablevehicle 106 or home control system 126.

The communication interfaces 348 provide for the interconnection andcommunication of the integrated mobile device 104 with mobile computingdevices 120, service provider(s) 122, home control systems 126,connectable vehicle(s) 106 and other vehicles 128 in the system 100. Thecommunication interfaces 348 include a vehicle network interface 350,wired communication network interface 352, wireless communicationnetwork interface 354, and sensor/tag/beacon interface 356.

The vehicle network interface 350 enables the integrated mobile device104 to communicate with vehicle sub-systems 116 over the vehiclenetwork(s) 108 and vehicle bus 202. The wired communication networkinterface 352 (including USB interface) enables the integrated mobiledevice 104 to communicate with external systems and devices, such as theconnectable vehicle 106, using a wired connection such as via USB. Thewireless communication network interface 354 enables the integratedmobile device 104 to communicate with external systems and devices, suchas the connectable vehicle(s) 106, the home control system(s) 126 andservice provider(s) 122, using a wireless connection. Thesensor/tag/beacon interface 356 enables the integrated mobile device 104to communicate with direct sensors 110 and networked sensors 114 of theconnectable vehicle 106. Similarly, the sensor/tag/beacon interface 356can also be used to communicate with various sensors and sub-systems ofthe home control system(s) 126.

FIG. 4 illustrates a block diagram 400 of example security credentials410, 412, 414 formed by the connectable vehicle 106 (or home controlsystem 126) and by the service provider 122 in conjunction withintegrated mobile device 104 for conducting example communications inthe communication system 100. The security credentials assist withauthentication and secure communication of information among the user401, the integrated mobile device 104, the connectable vehicle(s) 106,the service provider(s) 122, the home control system(s) 126, as well asother systems and devices described herein.

As illustrated in FIG. 4, security credentials X_(A) 402 of user 401 canbe provided to the integrated mobile device (IMD) 104. The securitycredentials X_(A) 402 acquired from user 401 can be any one of a widearray of security credentials, such as signatures and hash functionsrepresenting a variety of biometric credentials (e.g., fingerprint,voice sample, breath sample, facial image, EEG sample, ECG sample, keyedpasswords, timed key signatures, and other biometric securitycredentials).

After acquiring the security credentials X_(A) 402 from user 401, theintegrated mobile device 104 authenticates the user's securitycredentials against security credentials stored by the integrated mobiledevice 104, such as in the certificate data store 306. While not shownor described in detail herein, the stored security credentials can beone or more of the foregoing security credentials that are provided bythe user 401 during a user-IMD set up process or service providerprovisioning conducted previously to the authentication.

The security credentials can be stored in their native version or as arepresentative version (e.g., a representative signature, hash value ofa hash function, or another representative version of the securitycredentials). If the security credentials are stored as a representativeversion, then the integrated mobile device 104 can convert the acquiredsecurity credentials X_(A) 402 into a representative version forcomparison against the stored representative version of the securitycredentials for authentication purposes.

After authenticating the user 401, the integrated mobile device 104combines the user security credentials X_(A) 402 (e.g., native versionor representative version) with security credentials X_(B) 404 of theintegrated mobile device 104 to form dual security credentials X 410(e.g., duo security credentials). Dual security credentials X 410 can bethe result of a cryptographic function on X_(A) and X_(B), e.g.,X=E_(XB)(X_(A)). Different cryptographic functions can be used (e.g.,MD5, SHA1, SHA2, and other cryptographic functions). While not as stronga result as with cryptography, the dual security credentials X 410 canbe the result of a concatenation function on X_(A) 402 and X_(B) 404, oranother combination of X_(A) 402 and X_(B) 404. The security credentialsX_(B) 404 of the integrated mobile device 104 can be stored in thecertificate data store 306.

In one example embodiment, the integrated mobile device 104 can transmitthe dual security credentials X 410 to the connectable vehicle 106(e.g., security sub-system 204). The connectable vehicle 106authenticates dual security credentials X 410 against dual securitycredentials stored by connectable vehicle 106, such as in thecertificate data store 118. While not shown or described in detailherein, the stored dual security credentials were received and stored inthe secure storage 118 as a result of the user-IMD set up processconducted previously with respect to the integrated mobile device 104.It should be noted that in the home-based implementation, the homecontrol system 126 can similarly authenticate the dual securitycredentials X 410 against dual security credentials stored by homecontrol system 126 in a secure storage.

After authenticating the dual security credentials X 410, theconnectable vehicle 106 combines the dual security credentials X 410with security credentials X_(C) 406 of the connectable vehicle 106 toform triple security credentials Y 412 (e.g., triad securitycredentials). Security credentials Y 412 can be the result of acryptographic function on X 410 and X_(C) 406, e.g., Y=E_(XC)(X) orY=E_(XC)(E_(XB)(X_(A))). Different cryptographic functions can be used(e.g., MD5, SHA1, SHA2, and other cryptographic functions). While not asstrong a result as with cryptography, triple security credentials Y 412can be the result of a concatenation function on X 410 and X_(C) 406, oranother combination of X 410 and X_(C) 406. The security credentialsX_(C) 406 of the connectable vehicle 106 can be stored in the securestorage 118. It should be noted that in the home-based implementation,the home control system 126 can similarly combine the dual securitycredentials X 410 with security credentials stored by the home controlsystem 126 in the secure storage to form triple security credentials Y412 (e.g., triad security credentials).

The formation of the triple security credentials Y 412 represents thecombination (e.g., cryptographic result) of two prior authentications,which underpins a secure and trusted association between three (3)entities—user 401, integrated mobile device 104, and the connectablevehicle 106. Similarly, Y 412 can also represent a trusted associationbetween the user 401, the integrated mobile device 104, and the homecontrol system 126. In some example embodiments, the connectable vehicle106 (or home control system 126) can subsequently transmit the triplesecurity credentials Y 412 to the service provider 122 for subsequentauthentications provided by the service provider 122 of the dualsecurity credentials X 410, which are received by the service provider122 from the integrated mobile device 104. The triple securitycredentials Y 412 can be stored by the service provider 122 in itscertificate data store 124 for future authentication and secure sessioncreation.

In another example embodiment, the integrated mobile device 104 cantransmit the dual security credentials X 410 to the service provider122. The service provider 122 authenticates dual security credentials X410 against dual security credentials stored by service provider 122,such as in the secure storage 124. While not shown or described indetail herein, the stored dual security credentials were received andstored in the secure storage 124 as a result of the user-IMD set upprocess or provisioning conducted previously with respect to theintegrated mobile device 104.

After authenticating the dual security credentials X 410, the serviceprovider 122 combines the dual security credentials X 410 with securitycredentials X_(D) 408 of the service provider 122 to form triplesecurity credentials Y′ 414 (e.g., triad security credentials). Securitycredentials Y′ 414 can be the result of a cryptographic function on X410 and X_(D) 408, e.g., Y=E_(XD)(X) or Y=E_(XD)(E_(XB)(X_(A))).Different cryptographic functions can be used (e.g., MD5, SHA1, SHA2,and other cryptographic functions). While not as strong a result as withcryptography, triple security credentials Y′ 414 can be the result of aconcatenation function on X 410 and X_(D) 408, or another combination ofX 410 and X_(D) 408. The security credentials X_(D) 408 of the serviceprovider 122 can be stored in the secure storage 124.

The formation of the triple security credentials Y′ 414 represents thecombination (e.g., cryptographic result) of two prior authentications,which underpins a secure and trusted association among three (3)entities—user 401, integrated mobile device 104, and the serviceprovider 122. In some example embodiments, the service provider 122 cansubsequently transmit the triple security credentials Y′ 414 to theconnectable vehicle 106 for subsequent authentications provided by theconnectable vehicle 106 of the dual security credentials X 410, whichare received by the connectable vehicle 106 from the integrated mobiledevice 104. The triple security credentials Y′ 414 can be stored by theconnectable vehicle 106 in its certificate data store 118 for futureauthentication and secure session creation. It should be noted that insome example home-based embodiments, the service provider 122 cansubsequently transmit the triple security credentials Y′ 414 to the homecontrol system 126 for subsequent authentications provided by the homecontrol system 126 of the dual security credentials X 410, which arereceived by the home control system 126 from the integrated mobiledevice 104. The triple security credentials Y′ 414 can be stored by thehome control system 126 in its secure storage for future authenticationand secure session creation.

The triple security credentials Y 412 can be used to securitize orauthenticate any command or request (hereinafter either or bothreferenced as instruction) issued by the connectable vehicle 106 (orhome control system 126) to service provider 122 or the integratedmobile device 104, or by the integrated mobile device 104 to connectablevehicle 106 (or home control system 126) and the service provider 122.The instruction can include a context-based informational displayinstruction or context-based control instruction. The foregoingrepresents a tight and secure association among the three (3) entities:the connectable vehicle 106 (or home control system 126), the integratedmobile device 104 and the user 401. Similarly, triple securitycredentials Y′ 414 can be used to securitize or authenticate any commandor request (instruction) issued by the service provider 122 to theconnectable vehicle 106 or the integrated mobile device 104, or by theintegrated mobile device 104 to connectable vehicle 106 and the serviceprovider 122. It should be noted that in example home-based embodiments,the triple security credentials Y′ 414 can be used to securitize orauthenticate any instruction issued by the service provider 122 to thehome control system 126 or the integrated mobile device 104, or by theintegrated mobile device 104 to the home control system 126 and theservice provider 122.

FIG. 5 illustrates a block diagram of example security credentialsformed by the by the integrated mobile device 104 based on securitycredentials of the connectable vehicle 106 (or home control system 126)and security credentials of the service provider 122 for conductingexample communications in the communication system 100. The securitycredentials assist with authentication and secure communication ofinformation among the user 501, the integrated mobile device 104, theconnectable vehicle(s) 106, the service provider(s) 122, the homecontrol system(s) 126, as well as other systems and devices describedherein.

As illustrated in FIG. 5, security credentials X_(A) 502 of user 501 canbe provided to the integrated mobile device (IMD) 104. The securitycredentials X_(A) 502 acquired from user 501 can be any one of a widearray of security credentials, such as signatures and hash functionsrepresenting a variety of biometric credentials (e.g., fingerprint,voice sample, breath sample, facial image, EEG sample, ECG sample, keyedpasswords, timed key signatures, and other biometric securitycredentials).

After acquiring the security credentials X_(A) 502 from user 501, theintegrated mobile device 104 authenticates the user's securitycredentials against security credentials stored by the integrated mobiledevice 104, such as in the certificate data store 306. While not shownor described in detail herein, the stored security credentials can beone or more of the foregoing security credentials that are provided bythe user 501 during a user-IMD set up process or service providerprovisioning conducted previously to the authentication.

The security credentials can be stored in their native version or as arepresentative version (e.g., a representative signature, hash value ofa hash function, or another representative version of the securitycredentials). If the security credentials are stored as a representativeversion, then the integrated mobile device 104 can convert the acquiredsecurity credentials X_(A) 502 into a representative version forcomparison against the stored representative version of the securitycredentials for authentication purposes.

After authenticating the user 501, the integrated mobile device 104combines the user security credentials X_(A) 502 (e.g., native versionor representative version) with security credentials X_(B) 504 of theintegrated mobile device 104 to form dual security credentials X 510(e.g., duo security credentials). Dual security credentials X 510 can bethe result of a cryptographic function on X_(A) and X_(B), e.g.,X=E_(XB)(X_(A)). Different cryptographic functions can be used (e.g.,MD5, SHA1, SHA2, and other cryptographic functions). While not as stronga result as with cryptography, the dual security credentials X 410 canbe the result of a concatenation function on X_(A) 502 and X_(B) 504, oranother combination of X_(A) 502 and X_(B) 504. The security credentialsX_(B) 504 of the integrated mobile device 104 can be stored in thecertificate data store 306.

In one example embodiment, the connectable vehicle 106 transmitssecurity credentials X_(C) 506 to the integrated mobile device 104. Thesecurity credentials X_(C) 506 of the connectable vehicle 106 can bestored in its secure storage 118. The integrated mobile device 104combines the dual security credentials 510 with security credentialsX_(C) 506 of the connectable vehicle 106 to form triple securitycredentials Y 512 (e.g., triad security credentials). Securitycredentials Y 512 can be the result of a cryptographic function on X 510and X_(C) 506, e.g., Y=E_(XC)(X) or Y=E_(XC)(E_(XB)(X_(A))). Differentcryptographic functions can be used (e.g., MD5, SHA1, SHA2, and othercryptographic functions). While not as strong a result as withcryptography, triple security credentials Y 512 can be the result of aconcatenation function on X 510 and X_(C) 506, or another combination ofX 510 and X_(C) 506. It should be noted that in home-based embodiments,the home control system 126 can similarly transmit its securitycredentials (e.g., stored in its secure storage) to the integratedmobile device 104. The integrated mobile device 104 can then combine itsdual security credentials 510 with the security credentials of the homecontrol system 126 to form triple security credentials Y 512 (e.g.,triad security credentials).

The formation of the triple security credentials Y 512 represents thecombination (e.g., cryptographic result) of two prior authentications,which underpins a secure and trusted association between three (3)entities—user 501, integrated mobile device 104, and the connectablevehicle 106. Similarly, Y 512 can also represent a trusted associationbetween the user 501, the integrated mobile device 104, and the homecontrol system 126. In some example embodiments, the integrated mobiledevice 104 can subsequently transmit the triple security credentials Y512 to the service provider 122 for subsequent authentications providedby the service provider 122. The triple security credentials Y 512 canbe stored by the service provider 122 in its secure storage 124 forfuture authentication and secure session creation.

In another example embodiment, the service provider 122 transmitssecurity credentials X_(D) 506 to the integrated mobile device 104. Thesecurity credentials X_(D) 508 of the service provider 122 can be storedin its secure storage 124. The integrated mobile device 104 combines thedual security credentials X 510 with security credentials X_(D) 508 ofthe service provider 122 to form triple security credentials Y′ 514(e.g., triad security credentials). Security credentials Y′ 514 can bethe result of a cryptographic function on X 510 and X_(D) 508, e.g.,Y=E_(XP)(X) or Y=E_(XP)(E_(XB)(X_(A))). Different cryptographicfunctions can be used (e.g., MD5, SHA1, SHA2, and other cryptographicfunctions). While not as strong a result as with cryptography, triplesecurity credentials Y′ 514 can be the result of a concatenationfunction on X 510 and X_(D) 508, or another combination of X 510 andX_(D) 508.

The formation of the triple security credentials Y′ 514 represents thecombination (e.g., cryptographic result) of two prior authentications,which underpins a secure and trusted association among three (3)entities—user 501, integrated mobile device 104, and the serviceprovider 122. In some example embodiments, the integrated mobile device104 can subsequently transmit the triple security credentials Y′ 514 tothe connectable vehicle 106 for subsequent authentications andsecuritization of display and control instructions between theconnectable vehicle 106 (or home control system 126) and the integratedmobile device 104. The triple security credentials Y′ 514 can be storedby the connectable vehicle 106 in its secure storage 118 for futureauthentication and secure session creation. In home-based environments,the triple security credentials Y′ 514 can similarly be stored by thehome control system 126 in its secure storage for future authenticationand secure session creation.

The triple security credentials Y 512 can be used to securitize orauthenticate any command or request (instruction) issued by theconnectable vehicle 106 (or home control system 126) to service provider122 or the integrated mobile device 104, or by the integrated mobiledevice 104 to connectable vehicle 106 (or home control system 126) andthe service provider 122. This represents a tight and secure associationamong the three (3) entities: the connectable vehicle 106 (or homecontrol system 126), the integrated mobile device 104 and the user 501.Similarly, triple security credentials Y′ 514 can be used to securitizeor authenticate any command or request (instruction) issued by theservice provider 122 to the connectable vehicle 106 or the integratedmobile device 104, or by the integrated mobile device 104 to connectablevehicle 106 and the service provider 122. It should be noted that inexample home-based embodiments, the triple security credentials Y′ 514can be used to securitize or authenticate any instruction issued by theservice provider 122 to the home control system 126 or the integratedmobile device 104, or by the integrated mobile device 104 to the homecontrol system 126 and the service provider 122.

FIG. 6 is a flowchart that illustrates an example method 600 of formingsecurity credentials in accordance with FIG. 4 to conduct example secureand authenticated communications in the communication system 100.

The method 600 begins at operation 602. At operation 604, the integratedmobile device 104 receives security credentials (e.g., X_(A)) from theuser 401. At operation 606, the integrated mobile device 104authenticates the security credentials (e.g., X_(A)) received from theuser 401. At operation 608, a determination is made as to whether theuser 401 is authorized with respect to the integrated mobile device 104,e.g., to perform one or more commands or requests.

If is it determined at operation 608 that the user 401 is authorized,the method continues at operation 610, where the integrated mobiledevice 104 accesses security credentials associated with the integratedmobile device 104 (e.g., X_(B)), such as from certificate data store306. At operation 612, the integrated mobile device 104 combines thesecurity credentials (e.g., X_(A)) of the user 401 and the securitycredentials (e.g., X_(B)) of the integrated mobile device 104 to formdual security credentials (e.g., E_(XB)(X_(A))), as described withreference to FIG. 4, for example. However, if is it determined atoperation 608 that the user 401 is not authorized, the method 600 endsat operation 632.

At operation 614, a determination is made by the integrated mobiledevice 104 as to which entity (or system) is to conduct externalauthentication of the dual security credentials (e.g., E_(XB)(X_(A))).If it is determined that vehicle authentication is to be performed, thenthe method 600 continues at operation 616, where the integrated mobiledevice 104 transmits the dual security credentials (e.g., E_(XB)(X_(A)))to the connectable vehicle 106. At operation 618, the integrated mobiledevice 104 receives an authentication result from the connectablevehicle 106. The authentication result includes an indication of whetherthe dual security credentials (e.g., E_(XB)(X_(A))) were authorized, andcan further include the triple security credentials (e.g.,(E_(XC)(E_(XB)(X_(A)))) formed by the connectable vehicle 106 uponauthorization of the dual security credentials.

At operation 620, a determination is made based on the authenticationresult received from the connectable vehicle 106, as to whether the dualsecurity credentials (e.g., E_(XB)(X_(A))) were authorized by theconnectable vehicle 106. If it is determined at operation 620 that thedual security credentials (e.g., E_(XB)(X_(A))) were authorized, themethod continues at operation 622, where the triple security credentials(e.g., (E_(XC)(E_(XB)(X_(A)))) formed by the connectable vehicle 106 areutilized to communicate securely among the integrated mobile device 104,the connectable vehicle 106, and the service provider 122. For example,the triple security credentials (e.g., (E_(XC)(E_(XB)(X_(A)))) can beused to encrypt the communication messages, or one or more sessionsestablished using the triple security credentials. Thereafter, themethod 600 ends at operation 632. If it is determined at operation 620that the dual security credentials (e.g., E_(XB)(X_(A))) were notauthorized, the method similarly ends at operation 632.

If at operation 614 it is determined that service providerauthentication is to be performed, then the method 600 continues atoperation 624 where the integrated mobile device 104 transmits the dualsecurity credentials (e.g., E_(XB)(X_(A))) to the service provider 122.At operation 626, the integrated mobile device 104 receives anauthentication result from the service provider 122. The authenticationresult includes an indication of whether the dual security credentials(e.g., E_(XB)(X_(A))) were authorized, and can further include thetriple security credentials (e.g., (E_(XD)(E_(XB)(X_(A)))) formed by theservice provider 122 upon authorization of the dual securitycredentials.

At operation 628, a determination is made based on the authenticationresult received from the service provider 122, as to whether the dualsecurity credentials (e.g., E_(XB)(X_(A))) were authorized by theservice provider 122. If it is determined at operation 628 that the dualsecurity credentials (e.g., E_(XB)(X_(A))) were authorized, the methodcontinues at operation 630, where the triple security credentials (e.g.,(E_(XD)(E_(XB)(X_(A)))) formed by the service provider 122 are utilizedto communicate securely among the integrated mobile device 104, theconnectable vehicle 106, and the service provider 122. For example, thetriple security credentials (e.g., (E_(XD)(E_(XB)(X_(A)))) can be usedto encrypt the communication messages, or one or more sessionsestablished using the triple security credentials. Thereafter, themethod 600 ends at operation 632. If it is determined at operation 628that the dual security credentials (e.g., E_(XB)(X_(A))) were notauthorized, the method similarly ends at operation 632.

FIG. 7 is a flowchart that illustrates an example method 700 of formingsecurity credentials in accordance with FIG. 5 to conduct example secureand authenticated communications in the communication system 100.

The method 700 begins at operation 602. At operation 704, the integratedmobile device 104 receives security credentials (e.g., X_(A)) from theuser 501. At operation 706, the integrated mobile device 104authenticates the security credentials (e.g., X_(A)) received from theuser 501. At operation 708, a determination is made as to whether theuser 501 is authorized with respect to the integrated mobile device 104,e.g., to perform one or more commands or requests.

If is it determined at operation 708 that the user 501 is authorized,the method 700 continues at operation 710, where the integrated mobiledevice 104 accesses security credentials associated with the integratedmobile device 104 (e.g., X_(B)), such as from certificate data store306. At operation 712, the integrated mobile device 104 combines thesecurity credentials (e.g., X_(A)) of the user 501 and the securitycredentials (e.g., X_(B)) of the integrated mobile device 104 to formdual security credentials (e.g., E_(XB)(X_(A))), as described withreference to FIG. 5, for example. However, if is it determined atoperation 708 that the user 501 is not authorized, the method 700 endsat operation 736.

At operation 714, a determination is made by the integrated mobiledevice 104 as to which entity (or system) is to conduct externalauthentication of the dual security credentials (e.g., E_(XB)(X_(A))).If it is determined that vehicle authentication is to be performed, thenthe method 700 continues at operation 716, where the integrated mobiledevice 104 transmits the dual security credentials (e.g., E_(XB)(X_(A)))to the connectable vehicle 106. At operation 718, the integrated mobiledevice 104 receives an authentication result from the connectablevehicle 106. The authentication result includes an indication of whetherthe dual security credentials (e.g., E_(XB)(X_(A))) were authorized, andcan further include the security credentials associated with theconnectable vehicle (e.g., X_(C)) provided upon authorization of thedual security credentials.

At operation 720, a determination is made based on the authenticationresult received from the connectable vehicle 106, as to whether the dualsecurity credentials (e.g., E_(XB)(X_(A))) were authorized by theconnectable vehicle 106. If it is determined at operation 720 that thedual security credentials (e.g., E_(XB)(X_(A))) were authorized, themethod continues at operation 722, where integrated mobile device 104forms the triple security credentials (e.g., (E_(XC)(E_(XB)(X_(A))))based on the dual security credentials (e.g., E_(XB)(X_(A))) and thesecurity credentials associated with the connectable vehicle (e.g.,X_(C)) provided by the connectable vehicle 106.

At operation 724, the triple security credentials (e.g.,(E_(XC)(E_(XB)(X_(A)))) formed by the integrated mobile device 104 areutilized to communicate securely among the integrated mobile device 104,the connectable vehicle 106, and the service provider 122. For example,the triple security credentials (e.g., (E_(XC)(E_(XB)(X_(A)))) can beused to encrypt the communication messages, or one or more sessionsestablished using the triple security credentials. Thereafter, themethod 700 ends at operation 736. If it is determined at operation 720that the dual security credentials (e.g., E_(XB)(X_(A))) were notauthorized, the method similarly ends at operation 736.

If at operation 714 it is determined that service providerauthentication is to be performed, then the method 700 continues atoperation 726 where the integrated mobile device 104 transmits the dualsecurity credentials (e.g., E_(XB)(X_(A))) to the service provider 122.At operation 728, the integrated mobile device 104 receives anauthentication result from the service provider 122. The result includesan indication of whether the dual security credentials (e.g.,E_(XB)(X_(A))) were authorized, and can further include the securitycredentials associated with the service provider 122 (e.g., X_(D))provided upon authorization of the dual security credentials.

At operation 730, a determination is made based on the authenticationresult received from the service provider 122, as to whether the dualsecurity credentials (e.g., E_(XB)(X_(A))) were authorized by theservice provider 122. If it is determined at operation 730 that the dualsecurity credentials (e.g., E_(XB)(X_(A))) were authorized, the method700 continues at operation 732, where mobile device 104 forms the triplesecurity credentials (e.g., (E_(XD)(E_(XB)(X_(A)))) based on the dualsecurity credentials (e.g., E_(XB)(X_(A))) and the security credentialsassociated with the service provider (e.g., X_(D)) provided by theservice provider 122.

At operation 734, the triple security credentials (e.g.,(E_(XD)(E_(XB)(X_(A)))) formed by the integrated mobile device 104 areutilized to communicate securely among the integrated mobile device 104,the connectable vehicle 106, and the service provider 122. For example,the triple security credentials (e.g., (E_(XD)(E_(XB)(X_(A)))) can beused to encrypt the communication messages, or one or more sessionsestablished using the triple security credentials. Thereafter, themethod 700 ends at operation 736. If it is determined at operation 730that the dual security credentials (e.g., E_(XB)(X_(A))) were notauthorized, the method similarly ends at operation 736.

It should be noted that the foregoing functionality of the connectedvehicle 106 described with reference to FIGS. 6 and 7 can similarly beperformed by the home control system 126. Moreover, in view of FIGS.4-7, seamless mobility can be provided to the user 401, 501, as the user(integrated mobile device 104) transitions between the connectablevehicle 106 and a connected home (home control system 126), whileassuring authentication of the components and securitization ofinstructions among the components in the system 100 of FIG. 1.

FIG. 8 is a flowchart that illustrates an example method 800 ofproviding context-based control associated with the connectable vehicle106.

The method 800 provides contextualized control of vehicle and serviceprovider functions on the integrated mobile device 104, typicallywearable by a vehicle operator. Such tight integration of vehiclesecurity, infotainment and control functions with the user provides forenhanced security and usability, while enabling novel ways ofcontext-based user-vehicle and user-service provider interactions.Specifically, the described improvements enable context-based controlfunctionality by integrating the user 401, 501 of the integrated mobiledevice 104 with the various systems, sub-systems and/or components ofthe connectable vehicle 104, the home control system 126, and theservice provider 122.

In this example embodiment, the context can be defined as one or more ofthe following factors: 1) integrated mobile device location withreference to the vehicle, home control system 126, and/or theirsub-systems and components; 2) user-vehicle/user-house functionalactivity category; and 3) user-service provider functional activitycategory. Given a certain user input, different contexts can result indifferent types of control/display/security functional activities (oractions) undertaken by one or more systems. Additionally oralternatively, the context can include factors as described herein withreference to FIG. 1.

The method 800 begins at operation 802, where an initiation indicator isobtained or otherwise received by the integrated mobile device 104. Theinitiation indicator can be a user interrupt or a system interruptreceived by the integrated mobile device 104. For example, theinitiation indicator can be an input by the user 401, 501 with respectto the integrated mobile device 104, or can be a system indicatorautomatically generated as a result of anomalous user and/or vehicleactivity (e.g., motion, biometric and/or other data associated withuser, telemetry and/or other data associated with the vehicle andobtained over the vehicle network(s) 108 from various vehiclesub-systems), or can be a system indicator automatically generated bythe home control system 126 (e.g., state change or activity detection).

At operation 804 a determination is made as to whether the initiationindicator is a user initiation indicator or a system initiationindicator. If it is determined at operation 804 that the indicator is auser initiation indicator, then the method 800 continues at operation806, where the integrated mobile device 104 receives control input fromthe user (user input), e.g., voice, video, breath sample, EEG sample,ECG sample, button input, button sequence and/or timed input, other typeof input, or a combination of different inputs.

At operation 808, the integrated mobile device 104 determines whetherthe current position of the integrated mobile device 104 in reference tothe connectable vehicle 106 (e.g., body frame or component) isavailable. If it is determined at operation 808 that the currentposition is available, then at operation 810 the integrated mobiledevice 104 accesses the current position of the integrated mobile device104. The current position of the integrated mobile device 104 can bedetermined based on proximity to a sensor 110, 114, triangulation amongvarious sensors 110, 114, or another mechanism. For example, the currentposition can be obtained from various input devices 308 and processingdevices 326 of the integrated mobile device 104, e.g., imagerecognition, GPS positioning, accelerometer information, audioinformation, as well as information from other input devices 308 andprocessing devices 326, and various combinations of information. Thecurrent position can be used to update a default position of theintegrated mobile device 104, and the current position can be determinedby integrated mobile device 104 at various intervals (e.g., everysecond, or another less/more frequent interval).

If it is determined at operation 808 that the current position is notavailable, then at operation 812 the integrated mobile device 104retrieves a default position of the integrated mobile device 104. Atoperation 814, a context associated with the control input is determinedbased at least on the position (current or default) of the integratedmobile device 104. Specifically, a default context can be determinedbased on the default position and a current context can be determinedbased on the current position. As already described herein, context canalso include multiple other factors, state variables of systems andcomponents, user's activity and location of the integrated mobile device104. Certain portions of the context can be provided by the vehiclesubsystems 116, sensors 110, 114 and other controls. Other portions ofcontext can further be determined by the service provider 122 based oncommunications with connectable vehicle 106, other vehicle(s) 128,integrated mobile device 104, home control system(s) 126 and mobilecomputing device(s) 120.

Now with reference to operation 804, if it is determined that theindicator is a system initiation indicator, then the method 800continues at operation 816, where a determination is made as to whetherthe system initiation indicator provides a context for such initiation.An example of a system initiation indicator is described below withreference to FIG. 10. If it is determined at operation 816 that thecontext is provided, then the method 800 continues at operation 822.Alternatively, if it is determined at operation 816 that the context isnot provided, then at operation 818 control input is requested from theuser based on the system initiation indicator, such as for example,requesting that the user 401, 501 provide a breath sample. Other controlinputs can be requested, such as voice, video, button input, buttonsequence and/or timed input, biometric input (e.g., from biometricprocessing device 334), other type of input, or a combination ofdifferent inputs. At operation 820, a context associated with thecontrol input is determined based on the system initiation indicator. Anexample method of determining the context is described below withreference to FIG. 11.

At operation 822, a determination is made as to whether the contextrequires confirmation by the user 401, 501. For example, the contextthat was determined as a result of user initiation can be allowed to beconfirmed by the user 401, 501, while the context provided or determinedas a result of system initiation may not allow the user 401, 501 toconfirm such context. In those situations where several possiblecontexts are plausible, it can be desirable that the user confirm aparticular context or select a preferred context. For example, considerthat a certain pattern in movement or displacement of the integratedmobile device 104 indicates a context of “radio volume control”, “cabintemperature control”, and/or other possible contexts. One of thecontexts determined to be appropriate can be presented to the user 401,501 for confirmation. Alternatively, the possible contexts can bepresented to user 401, 501 for selection of the appropriate contextpreferable to the user.

If at operation 822 it is determined that the context requiresconfirmation, at operation 824 the integrated mobile device 106 queriesthe user 401, 501 whether the context is acceptable. If at operation 824it is determined that the context is acceptable, then at operation 826 avehicle command (instruction) is generated based on the received controlinput (user input) and the determined or provided context. At operation828 the vehicle command (instruction) is indicated via the intergradedmobile device 104, e.g., via video, audio or actuation.

At operation 830, a determination is made as to whether the systeminitiation indicator was received. If it is determined at operation 830that the system initiation indicator was received, then at operation 834the vehicle command (instruction) is transmitted to the connectablevehicle 106 using, for example, a session established between theintegrated mobile device 104 and the connectable vehicle 106, which isbased on triple security credentials as described with reference toFIGS. 4 and 5. The connectable vehicle 106 receives and executes thecommand (instruction) to control a component or function of theconnectable vehicle 106.

If however it is determined at operation 830 that the system initiationindicator was not received, then at operation 832 a determination ismade as to whether the command is acceptable to the user 401, 501. Ifthe command is acceptable at operation 832, the method 800 continues atoperation 834. Alternatively, if the command is not acceptable atoperation 832, then the method continues at operation 806 for user toestablish a different context associated with its control input, suchthat a different command could be formed.

It should be noted that operations 826-834 can be related to a commandtargeting the home control system 126, or a component thereof, wherein acommand can be transmitted to one or more home appliances over acommunication network(s) 102. For example, a certain pattern of shakingthe integrated mobile 104 by the user 401, 501 in relation toconnectable vehicle 106 (other activity or selection by the user) canresult in a context related to turning off all appliances controlled bythe home control system 126.

At operation 836, a determination is made as to whether an indication ofacknowledgement is required from the connectable vehicle 106 or homecontrol system 126. If it is determined at operation 836 that theindication of acknowledged is required, then at operation 840 theintegrated mobile device 104 indicates the indication of acknowledgementreceived from the connectable vehicle 106. Thereafter, the method 800ends at operation 858.

Now further with reference to operation 824, if it is determined thatthe context is not acceptable, then at operation 842 a determination ismade as to whether context selection is enabled at the integrated mobiledevice 104. If it is determined that context selection is enabled at theintegrated mobile device 104, then at operation 844 one or more contexts(e.g., list of contexts) associated with the control input are accessedor retrieved by the integrated mobile device 104, such as contextsdetermined by the processor 302 as a result of interrogating inputdevices 308 and/or processing device 326, or resulting from theprocessor 302 communicating with one or more of the mobile computingdevice 120, service provider(s) 122, home control system(s) 126, andother vehicle(s) 128 over the communication network(s) 102. At operation846 the one or more contexts retrieved are indicated by the integratedmobile device to the user 401, 501. At operation 848 the user selects acontext from the contexts indicated. Thereafter method 800 continueswith operations 826-858 based on the context as selected.

If it is determined that context selection is not enabled at theintegrated mobile device 104, then at operation 850 a determination ismade as to whether context selection is enabled at the connectablevehicle 106. If it is determined that context selection is enabled atthe connectable vehicle 106, then at operation 852 one or more contexts(e.g., list of contexts) associated with the control input are requestedand received by the integrated mobile device 104 from the connectablevehicle 106. In home-based embodiments, the operations 850, 852 aredirected to the home control system 126 and the contexts are receivedfrom the home control system 126. The method 800 continues at operations846 and 848 to allow the user 401, 501 to select a context associatedwith the control input. Thereafter method 800 continues with operations826-858 based on the context as selected.

If it is determined that context selection is not enabled at theconnectable device 106 or home control system 126, then at operation 854a determination is made as to whether context selection is enabled atthe service provider 122. If it is determined that context selection isenabled at the service provider 122, then at operation 856 one or morecontexts (e.g., list of contexts) associated with the control input arerequested and received by the integrated mobile device 104 from theservice provider 122. The method 800 continues at operations 846 and 848to allow the user 401, 501 to select a context associated with thecontrol input. Thereafter method 800 continues with operations 826-858based on the context as selected.

If it is determined at operation 854 that context selection is notenabled at the service provider 122, the method 800 ends at operation858. In some embodiments, if no context is determined to be available asa result of operations 842, 850, 854, then the integrated mobile device104 can indicate that no context was available (e.g., via video, audioor actuation) before the method 800 ends. Alternatively, a defaultcontext can be selected and the method 800 continued at operation 826.In some embodiments, the default context can also be provided by thehome control system(s) 126, e.g., from components of the home controlsystem 126 as impacted by various sensors or actuators of the homecontrol system 126 and associated data elements.

The functionality of the foregoing method 800 can be implemented, and insome implementations adapted, to perform one or more other context-basedcontrols associated with the connectable vehicle 106 or the home controlsystem 126, such as for example, remote vehicle start using passcodeinput/biometric input, opening of outside door and turning off asecurity system of a home associated with the home control system 126,recoding and/or display of audio/video from input devices 308 ofintegrated mobile device 104 by the connectable vehicle 106 or acomponent (e.g., DVD recorder) of the home control system 126,display/projection by the output device 336 of the integrated mobiledevice 104 of audio/visual data from the connectable vehicle 106 or acomponent (e.g., camera) of the home control system 126. In otherexamples, as the context associated with the home control system 126changes, various context selection confirmation functions can bepresented to the user 401, 501 via output devices 336 of the integratedmobile device 104. Moreover, the commands (control instructions)generated at operation 826 can thus be impacted by a diverse set ofcontexts determined by various systems, devices and components in thesystem 100.

FIG. 9 is a flowchart that illustrates an example method 900 ofproviding context-based informational indication associated with theconnectable vehicle 106 or a home control system 126. Context-basedinformation indication is also referred to herein as contextualizedinformation rendering or shaping.

The method 900 provides contextualized shaping or rendering ofinformation on the integrated mobile device 104, typically wearable by avehicle operator. Such tight integration of vehicle security,infotainment and control functions with the user provides for enhancedsecurity and usability, while enabling novel ways of context-baseduser-vehicle and user-service provider interactions. Specifically, thedescribed improvements enable context-based display functionality byintegrating the user 401, 501 of the integrated mobile device 104 withthe various systems, sub-systems and/or components of the connectablevehicle 104, the home control system 126, and the service provider 122.

The method 900 begins at operation 902, where an initiation indicator isobtained or otherwise received by the integrated mobile device 104. Theinitiation indicator can be a user interrupt or a system interruptreceived by the integrated mobile device 104. For example, theinitiation indicator can be an input by the user 401, 501 with respectto the integrated mobile device 104, or can be a system indicatorautomatically generated as a result of anomalous user and/or vehicleactivity (e.g., motion, biometric and/or other data associated withuser, telemetry and/or other data associated with the vehicle). Theinitiation indicator can also be generated by the home control system126 as a result of home intrusion activity detection or change in stateassociated with one or more components of the home control system 126.

At operation 904 a determination is made as to whether the initiationindicator is a user initiation indicator or a system initiationindicator. If it is determined at operation 904 that the indicator is auser initiation indicator, then the method 900 continues at operation906, where the integrated mobile device 104 receives user input from theuser (e.g., voice, video, breath sample, EEG sample. ECG sample, buttoninput, button sequence and/or timed input, other type of input, or acombination of different inputs).

At operation 908, the integrated mobile device 104 determines whetherthe current position of the integrated mobile device 104 in reference tothe connectable vehicle 106 is available. If it is determined atoperation 908 that the current position is available, then at operation910 the integrated mobile device 104 accesses the current position ofthe integrated mobile device 104. The current position of the integratedmobile device 104 can be determined based on proximity to a sensor 110,114, triangulation among various sensors 110, 114, or another mechanism.For example, the current position can be obtained from various inputdevices 308 and processing devices 326 of the integrated mobile device104, e.g., image recognition, GPS positioning, accelerometerinformation, audio information, as well as information from other inputdevices 308 and processing devices 326, and various combinations ofinformation. The current position can be used to update a defaultposition of the integrated mobile device 104, and the current positioncan be determined by the integrated mobile device 104 at variousintervals (e.g., every second, or another less/more frequent interval).

If it is determined at operation 908 that the current position is notavailable, then at operation 912 the integrated mobile device 104retrieves a default position of the integrated mobile device 104. Atoperation 914, a context associated with the user input is determinedbased on the position (current or default) of the integrated mobiledevice 104. Specifically, a default context can be determined based onthe default position and a current context can be determined based onthe current position. As already described herein, context can alsoinclude multiple other factors, state variables of systems andcomponents, user's activity and location of the integrated mobile device104. Certain portions of the context can be provided by the vehiclesubsystems 116, sensors 110, 114 and other controls. Other portions ofcontext can further be determined by the service provider 122 based oncommunications with connectable vehicle 106, other vehicle(s) 128,integrated mobile device 104, home control system(s) 126 and mobilecomputing device(s) 120.

Now with reference to operation 904, if it is determined that theindicator is a system initiation indicator, then the method 900continues at operation 916, where a determination is made as to whetherthe system initiation indicator provides a context. An example of asystem initiation indicator is described below with reference to FIG.10. If it is determined at operation 916 that the context is provided,then the method 900 continues at operation 922.

Alternatively, if it is determined at operation 916 that the context isnot provided, then at operation 918 control input is requested from theuser 401, 501 based on the system initiation indicator, such as forexample, requesting that the user 401, 501 provide a breath sample.Other control inputs can be requested, such as voice, video, buttoninput, button sequence and/or timed input, other type of input, or acombination of different inputs. At operation 920, a context associatedwith the control input is determined based on the system initiationindicator. An example method of determining the context is describedbelow with reference to FIG. 11.

At operation 922, a determination is made as to whether the contextrequires confirmation by the user 401, 501. For example, the contextthat was determined as a result of user initiation can be allowed to beconfirmed by the user 401, 501, while the context provided or determinedas a result of system initiation may not allow the user 401, 501 toconfirm such context. As already described herein, in those situationswhere several possible contexts are plausible, it can be desirable thatthe user confirm a particular context or select a preferred context. Forexample, consider that a certain pattern in movement or displacement ofthe integrated mobile device 104 indicates a context of “radio volumecontrol”, “cabin temperature control”, and/or other possible contexts.One of the contexts determined to be appropriate can be presented to theuser 401, 501 for confirmation. Alternatively, the possible contexts canbe presented to user 401, 501 for selection of the appropriate contextpreferable to the user.

If at operation 922 it is determined that the context requiresconfirmation, then at operation 924 the integrated mobile device 104queries the user 401, 501 as to whether the context is acceptable. If atoperation 924 it is determined that the context is acceptable, then atoperation 926 a query (instruction) is generated based on the receiveduser input, received initiation indicator, and the determined orprovided context. In some embodiments, the query can optionally beindicated to the user 401, 501 by the integrated mobile device 104.

At operation 928, a determination is made as to whether a systeminitiation indicator was received. If it is determined at operation 928that the system initiation indicator was received, then at operation 932the query (instruction) is transmitted to the connectable vehicle 106using, for example, a session established between the integrated mobiledevice 104 and the connectable vehicle 106, which is based on triplesecurity credentials as described with reference to FIGS. 4 and 5. Theconnectable vehicle 106 executes the query (instruction) and generates aresult of the query (instruction) in relation to a component or functionof the connectable vehicle 106. Thereafter, at operation 934 theintegrated mobile device 104 receives the result of the query (e.g.,vehicle code(s) from the connectable vehicle 106, codes (results) ofother components of system 100, and/or other information intended forconsumption by the user 401, 501). Accordingly, the query and the resultof the query are both functions of the context.

If however it is determined at operation 928 that the system initiationindicator was not received, then at operation 930 a determination ismade as to whether the query (instruction) is acceptable to the user401, 501. If the query (instruction) is acceptable at operation 930, themethod 900 continues at operation 932. Alternatively, if the query(instruction) is not acceptable at operation 930, then the method 900continues at operation 906 for the user 401, 501 to establish adifferent context associated with its user input, such that a differentquery (instruction) could be formed.

It should be noted that the operations 926-934 can be related to a querytargeting the home control system 126, or a component thereof, wherein aquery can be transmitted to one or more home appliances over acommunication network(s) 102. For example, a certain pattern of shakingthe integrated mobile 104 by the user 401, 501 in relation toconnectable vehicle 106 (other activity or selection by the user) canresult in a context related to obtaining a status of a system or anappliance controlled by the home control system 126.

At operation 936, a determination is made as to whether the result ofthe query (instruction) received from the connectable vehicle 106 (orhome control system(s) 126, or service provider(s) 122, or othervehicle(s) 128) is in a format that is to be indicated or rendered tothe user 401, 501. If it is determined at operation 936 that the resultis in the format to be indicated (rendered), then at operation 942 theintegrated mobile device 104 indicates the result to the user 401, 501,such as via one or more of video, audio and actuation using one or moreof the output devices 336 of the integrated mobile device 104. If it isdetermined at operation 936 that the result is not in the format to beindicated, then at operation 938 a determination is made as to whether alook-up using the service-provider 122 is enabled. The service provider122 can assist in translating (or shaping) the result (e.g., vehiclecode(s) of connectable vehicle 106 and/or code(s) of components of homecontrol systems 126) to a format more easily consumable or preferred bythe user 401, 501.

If at operation 938 it is determined that service-provider look-up isenabled, then at operation 940 the integrated mobile device 104transmits the result of the query (e.g., vehicle code(s) or componentcode(s)) to the service provider 122 and receives a shaped (readable orunderstandable) result that is associated with result which was not in aformat to be indicated or rendered. The method 900 continues atoperation 942 to indicate or render the shaped result to the user 401,501, such as via one or more video, audio and/or actuation using one ormore of the output devices 336 of the integrated mobile device 104.

However, if at operation 938 it is determined that service-providerlook-up is not enabled, then method 900 also continues at operation 942,where the integrated mobile device 104 indicates or renders thenon-shaped result (e.g., vehicle code(s) or component code(s)) to theuser 401, 501, such as via one or more video, audio and/or actuationusing one or more of the output devices 336 of the integrated mobiledevice 104.

At operation 944, a determination is made as to whether acknowledgementof the indicated/rendered result (or shaped result) is required from theuser 401, 501. If it is determined at operation 944 that acknowledgementof the indicated/rendered result or shaped result is required by theuser, then at operation 946 the integrated mobile device 104 collects orreceives such acknowledgement from the user 401, 501 using one or moreof the input devices 308 of the integrated mobile device 104, andtransmits such acknowledgement received to the connectable vehicle 106,home control system 126, service provider 122, or other vehicle 128.Thereafter, the method 900 ends at operation 964.

Now further with reference to operation 924, if it is determined thatthe context is not acceptable, then at operation 948 a determination ismade as to whether context selection is enabled at the integrated mobiledevice 104. If it is determined that context selection is enabled at theintegrated mobile device 104, then at operation 950 one or more contexts(e.g., list of contexts) associated with the user input are accessed orretrieved by the integrated mobile device 104, such as contextsdetermined by the processor 302 as a result of interrogating inputdevices 308 and/or processing device 326, or resulting from theprocessor 302 communicating with one or more of the mobile computingdevice 120, service provide(s) 122, home control system(s) 126, andother vehicle(s) 128 over the communication network(s) 102. At operation952 the one or more contexts retrieved are indicated by the integratedmobile device to the user 401, 501. At operation 954 the user selects acontext from the contexts indicated. Thereafter method 900 continueswith operations 826-964 based on the context as selected.

If it is determined that context selection is not enabled at theintegrated mobile device 104, then at operation 956 a determination ismade as to whether context selection is enabled at the connectablevehicle 106. If it is determined that context selection is enabled atthe connectable vehicle 106, then at operation 958 one or more contexts(e.g., list of contexts) associated with the user input are requestedand received by the integrated mobile device 104 from the connectablevehicle 106. In home-based embodiments, the operations 956, 958 aredirected to the home control system 126 and the contexts are receivedfrom the home control system 126. The method 900 continues at operations952 and 954 to allow the user 401, 501 to select a context associatedwith the user input. Thereafter method 900 continues with operations926-964 based on the context as selected.

If it is determined that context selection is not enabled at theconnectable device 106 or the home control system 126, then at operation960 a determination is made as to whether context selection is enabledat the service provider 122. If it is determined that context selectionis enabled at the service provider 122, then at operation 962 one ormore contexts (e.g., list of contexts) associated with the control inputare requested and received by the integrated mobile device 104 from theservice provider 122. The method 900 continues at operations 952 and 954to allow the user 401, 501 to select a context associated with the userinput. Thereafter method 800 continues with operations 926-964 based onthe context as selected.

If it is determined at operation 960 that context selection is notenabled at the service provider 122, the method 900 ends at operation964. In some embodiments, if no context is determined to be available asa result of operations 948, 956, 960, then the integrated mobile device104 can indicate that no context was available (e.g., via video, audioor actuation) before the method 900 ends. Alternatively, a defaultcontext can be selected and the method 900 continued at operation 926.In some embodiments, the default context can also be provided by thehome control system(s) 126, e.g., from components of the home controlsystem 126 as impacted by various sensors or actuators of the homecontrol system 126 and associated data elements.

The functionality of the foregoing method 900 can be implemented, and insome implementations adapted, to perform one or more other context-baseddisplay associated with the connectable vehicle 106 or the home controlsystem 126, such as for example, displaying tire pressure when theintegrated mobile device 104 is in the proximity of a tire sensor ortire beacon 110, 114, displaying vehicle engine maintenance informationwhen the integrated mobile device 104 is in the proximity of thevehicle's engine 132, or displaying temperature of a home's thermostator temperature of a refrigerator/freezer. As the location of theintegrated mobile device changes in relation to the connectable vehicle106 (or home control system 126), the context can change, which changesthe queries (instructions) to the connectable vehicle 106 (or the homecontrol system 126) and the results of those queries can be shapeddifferently based on a service provider 122, as an example. For example,as the user 401, 501 transitions between the connectable vehicle 106 andthe home associated with home control system 126, the proximity of theintegrated of mobile device 104 to the home control system 126 cantrigger a system initiation indicator and generation of a context, whichenable the integrated mobile device 104 to issue a query (instruction)to the home control system 126 and to subsequently render to the user401, 501 a status of the home control systems 126.

FIG. 10 is a block diagram that illustrates generation of an examplesystem-based initiation indicator that can be used as input to thecontext-based control of the connectable vehicle 106 according to method800 of FIG. 8 or as a context-based informational indication associatedwith the connectable vehicle 106 according to method 900 of FIG. 9.

As illustrated in FIG. 10, the system 100 of FIG. 1 can further includeone or more activity profiling system(s) 1010, one or more activityprofile databases 1012, and one or more anomaly detection system 1014.The activity profiling system(s) 1010, the activity profile databases1012, and the anomaly detection system(s) 1014 can be hosted by one ofthe integrated mobile device 104, the connectable vehicle 106, theservice provider 122, the mobile computing device 120, or be distributedamongst two or more of the foregoing.

The activity profiling system(s) 1010 are configured to receive datastreams from devices of the integrated mobile device 104 (e.g., devices314, 316, 320 of FIG. 3), data streams from devices of the connectablevehicle 106 (e.g., sub-systems 116 of FIG. 2), and data streams from thesensors 110, 114 of connectable vehicle 106 to update user profile dataand/or vehicle profile data or information in the one or more activityprofile databases 1012. Similarly, data streams can also be received bythe activity profiling system(s) 1010 from the home control system 126(e.g., systems, sub-systems, components and sensors of home controlsystem 126), the service providers 122, and the other vehicles 128 toupdate the user and/or home profile data or information in the one ormore activity profile databases 1012 (including user profile data and/orvehicle profile data).

The activity profiling system(s) 1010 periodically updates the data inthe one or more activity profile database(s) 1012, e.g., the periodicupdate interval can be every T seconds, where T is equal to (or greaterthan) one (1) second. Different periodic update periods can be used. Theprofiling system(s) 1010 generates statistical informational elements(e.g., activity profile data 1011) that describe various user behaviors,vehicle behaviors, and home control system behaviors—using the datastream(s) 1002, 1004 from the device(s) of the integrated mobile device104—and the associated impacts on various vehicle behaviors—using datastream(s) 1006 from the sub-systems 116 of the connectable vehicle 106and sub-systems of the home control system 126.

For example, the statistical information elements (activity profile data1011) can include data concerning average acceleration (e.g., mean,variance, distribution), breaking distance (e.g., mean, variance,distribution), vehicle turn radius (e.g., mean, variance, distribution),as well as any other vehicle behaviors that are impacted by userbehaviors. The activity profiling system(s) 1010 can thus createuser/system behavior profile(s) 1011 and store the profile(s) in theactivity profile database(s) 1012 for future comparison and reference,in order to determine anomalies associated with the behavior of one ormore of the connectable vehicle 106, the home control systems 126, andthe user 401, 501.

The user behavior applied to vehicle controls (e.g., acceleration,steering, breaking, an/or other controls) can be expressed as behaviorof the connectable vehicle 106 and state of associated variables of thesub-systems of the connectable vehicle 106, as acquired by vehicle'ssub-systems 116 and communicated to the activity profiling system(s)1010 via data streams 1002, 1004 and 1006. Similarly, user behaviorapplied to the home control system 126 can be expressed as behavior ofthe home control system 126 and state of associated variables of thesub-systems of the home control system 126, as acquired by sub-systemsof the home control system 126 and communicated to the activityprofiling system(s) 1010 via data streams 1002, 1004 and one or moreother data streams associated with the sub-systems of the home controlsystem 126.

The anomaly detection system(s) 1014 receives live data streams 1008from one or more sources, including the integrated mobile device 104(e.g., from devices 314, 316, 320 of FIG. 3), the connectable vehicle106 (e.g., sub-systems 116 of FIG. 2), and the home control system 126(e.g., sub-systems of the home control system 126). Moreover, theanomaly detection system(s) 1014 periodically retrieves activity profiledata 1013 from the activity profile database(s) 1012 and utilizes itsanomaly detection algorithms to compare the live data streams 1008received against the activity profile data 1013 for anomalous activity.The periodic retrieval interval can be every L seconds, where L is equalto (or greater than) one (1) second. Different periodic retrievalperiods can be used. A plurality of anomaly detection algorithms existin a variety of learning systems, which can find applicability and usein the anomaly detection system(s) 1014.

The anomaly detection system(s) 1014 determines when distribution of thelive data stream 1008 differs from distribution of the activity profiledata 1013 by more than one or more threshold value(s). The anomalydetection system(s) 1014 can determine a type of anomaly, e.g., unusualacceleration patterns, unusual breaking patterns, unusual turningpatterns, etcetera. Based on the difference, anomaly detection system(s)1014 can trigger creation of an initiation indicator that can be inputto the context-based control of the connectable vehicle 106 according tomethod 800 of FIG. 8 or to the context-based informational indicationassociated with the connectable vehicle 106 according to method 900 ofFIG. 9.

For example, a difference over a first threshold value can be used toexecute context-based informational indication, while a difference overa second threshold value can be used to execute context-based control ofthe connectable vehicle 106. Other implementations can be used. Asignificant difference between user/vehicle profile (e.g., stored inactivity profile database(s) 1012) and live data stream(s) 1008 cancause the anomaly detection system(s) 1014 to notify the serviceprovider 122 and/or disable the connectable vehicle 106, which can beactivated by the integrated mobile device 104 or a sub-system 116 of theconnectable vehicle 106. A context can be provided as part of theinitiation indicator based on the type of anomaly or the thresholdexceeded when the live data stream(s) 1008 is compared against activityprofile data 1013 in the activity profile database(s) 1012.

FIG. 11 is a flowchart that illustrates an example method 1100 ofproviding an example context to control the connectable vehicle 106according to FIG. 8 or to provide informational indication associatedwith the connectable vehicle 106 according to FIG. 9.

As will be described below, the example context is a location-basedbreathalyzer functional activity that can be used to control theconnectable vehicle 106 according to FIG. 8 or as an informationalindication of user's sobriety according to FIG. 9, based with alcohollimits associated with the location.

The example method 100 starts at operation 1102. As an example, themethod 1100 can be invoked by operation 818 of FIG. 8 or by operation918 of FIG. 9, which requests the user 401, 501 to provide to a controlinput or a user input, respectively. In this example, the control inputor user input is a breath sample. In various embodiments, the controlinput or a user input can be different for different functionalactivities.

Accordingly, at operation 1104 the integrated mobile device 104 receivesa breath sample of the user 401, 501 from a biometric sensor device 316(e.g., breathalyzer). A determination is made at operation 1106 as towhether current location of the connectable vehicle 106 is available, asacquired a sub-system(s) 116 of the connectable vehicle 106. If it isdetermined that the vehicle location is available, then at operation1108 the integrated mobile device 104 accesses the current location ofthe connectable vehicle 106. If it is determined that the vehiclelocation is not available, then at operation 1110 the integrated mobiledevice 104 accesses the default location of the connectable vehicle 106,e.g., the last known position.

At operation 1112 a determination is made as to whether alcohol contentlimit (e.g., blood alcohol content legal limit for a person to drive avehicle) is available for the current location at the integrated mobiledevice 104. The legal limit of blood alcohol content (alcohol contentlimit) can differ by location (e.g., state, jurisdiction, or otherlocation). In some embodiments, the integrated mobile device 104 canstore a list of allowed alcohol content limits by location, or a defaultalcohol content limit associated with the different locations (e.g.,0.08, 0.04, or another alcohol content limit).

If it is determined at operation 1112 that the alcohol content limit isavailable at the integrated mobile device 104, then at operation 1114 adetermination is made as to whether the breath sample received atoperation 1104 is within the alcohol content limit for the currentlocation. If the breath sample is within the alcohol content limit, thenat operation 1116 a first context is generated, indicating that thebreath sample is within the alcohol content limit for the currentlocation. If the breath sample is not within the alcohol content limit,then at operation 1118 a second context is generated, indicating thatthe breath sample is not within the alcohol content limit for thecurrent location. At operation 1120 the context generated is returned,such as to operation 820 of FIG. 8 or operation 920 of FIG. 9.

If it is determined at operation 1112 that the alcohol content limit isnot available at the integrated mobile device 104, then at operation1122 a determination is made as to whether alcohol content limitdetermination functionality is enabled at the connectable vehicle 106(e.g. sub-systems 116). If it is determined that vehicle-based alcoholcontent limit determination functionality is enabled, then at operation1124 the alcohol content limit is accessed for the current location fromthe connectable vehicle 106, and the method 1100 continues withoperations 1114-120 to return a context.

If it is determined that vehicle-based alcohol content limitdetermination functionality is not enabled, then at operation 1126 adetermination is made as to whether alcohol content limit determinationfunctionality is enabled at the service provider 122. If it isdetermined that service provider-based alcohol content limitdetermination functionality is enabled, then at operation 1128 thealcohol content limit is accessed for the current location from theservice provider 122, and the method 1100 continues with operations1114-120 to return a context.

If it is determined that service provider-based alcohol content limitdetermination functionality is not enabled, then at operation 1130 adefault alcohol content limit is set by the integrated mobile device104, and the method 1100 continues with operations 1114-120 to return acontext.

The example method 1100 returns a context associated with location-basedbreathalyzer functional activity that can be used for context-basevehicle control of FIG. 8 or for context-based informational of FIG. 9.Thereafter, method 1100 ends at operation 1132.

FIG. 12 is a block diagram of an illustrative embodiment of a generalcomputer system 1200. The computer system 1200 can be implemented as orintegrated into the mobile device 104, connectable vehicle 106, mobiledevice 120, service provider 122, home control system 126, or othervehicles 126, illustrated of FIG. 1. The computer system 1200 caninclude a set of instructions that can be executed to cause the computersystem 1200 to perform any one or more of the methods or computer basedfunctions disclosed herein. The computer system 1200, or any portionthereof, may operate as a standalone device or may be connected, e.g.,using a network or other connection, to other computer systems orperipheral devices. For example, the computer system 1200 may beconnected other systems and device via network 102.

The computer system 1200 may also be implemented as or incorporated intovarious devices, such as a personal computer (PC), a tablet PC, apersonal digital assistant (PDA), a mobile device (e.g., smartphone), apalmtop computer, a laptop computer, a desktop computer, acommunications device, a control system, a web appliance, wearablecomputing device (e.g., bracelet, glasses, broach, etc.) or any othermachine capable of executing a set of instructions (sequentially orotherwise) that specify actions to be taken by that machine. Further,while a single computer system 1200 is illustrated, the term “system”shall also be taken to include any collection of systems or sub-systemsthat individually or jointly execute a set, or multiple sets, ofinstructions to perform one or more computer functions.

As illustrated in FIG. 12, the computer system 1200 may include aprocessor 1202, e.g., a central processing unit (CPU), agraphics-processing unit (GPU), or both. Moreover, the computer system1200 may include a main memory 1204 and a secure memory 1206 that cancommunicate with each other via a bus 1226. As shown, the computersystem 1200 may further include a video display unit 1210, such as aliquid crystal display (LCD), an organic light emitting diode (OLED), aflat panel display, a solid state display, or a cathode ray tube (CRT).Additionally, the computer system 1200 may include an input device 1212,such as a keyboard, and a cursor control device 1214, such as a mouse.The computer system 1200 can also include a disk drive (or solid state)unit 1216, a signal generation device 1222, such as a speaker or remotecontrol, and a network interface device 1208.

In a particular embodiment or aspect, as depicted in FIG. 12, the diskdrive (or solid state) unit 1216 may include a computer-readable medium1218 in which one or more sets of instructions 1220, e.g., software, canbe embedded. Further, the instructions 1220 may embody one or more ofthe methods or logic as described herein. In a particular embodiment oraspect, the instructions 1220 may reside completely, or at leastpartially, within the main memory 1204, the static memory 1206, and/orwithin the processor 1202 during execution by the computer system 1200.The main memory 1204 and the processor 1202 also may includecomputer-readable media.

In an alternative embodiment or aspect, dedicated hardwareimplementations, such as application specific integrated circuits,programmable logic arrays and other hardware devices, can be constructedto implement one or more of the methods described herein. Applicationsthat may include the apparatus and systems of various embodiments oraspects can broadly include a variety of electronic and computersystems. One or more embodiments or aspects described herein mayimplement functions using two or more specific interconnected hardwaremodules or devices with related control and data signals that can becommunicated between and through the modules, or as portions of anapplication-specific integrated circuit. Accordingly, the present systemencompasses software, firmware, and hardware implementations.

In accordance with various embodiments or aspects, the methods describedherein may be implemented by software programs tangibly embodied in aprocessor-readable medium and may be executed by a processor. Further,in an exemplary, non-limited embodiment or aspect, implementations caninclude distributed processing, component/object distributed processing,and parallel processing. Alternatively, virtual computer systemprocessing can be constructed to implement one or more of the methods orfunctionality as described herein.

It is also contemplated that a computer-readable medium includesinstructions 1220 or receives and executes instructions 1220 responsiveto a propagated signal, so that a device connected to a network 1224 cancommunicate voice, video or data over the network 1224. Further, theinstructions 1220 may be transmitted or received over the network 1224via the network interface device 1208.

While the computer-readable medium is shown to be a single medium, theterm “computer-readable medium” includes a single medium or multiplemedia, such as a centralized or distributed database, and/or associatedcaches and servers that store one or more sets of instructions. The term“computer-readable medium” shall also include any medium that is capableof storing, encoding or carrying a set of instructions for execution bya processor or that cause a computer system to perform any one or moreof the methods or operations disclosed herein.

In a particular non-limiting, example embodiment or aspect, thecomputer-readable medium can include a solid-state memory, such as amemory card or other package, which houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to capturecarrier wave signals, such as a signal communicated over a transmissionmedium. A digital file attachment to an e-mail or other self-containedinformation archive or set of archives may be considered a distributionmedium that is equivalent to a tangible storage medium. Accordingly, anyone or more of a computer-readable medium or a distribution medium andother equivalents and successor media, in which data or instructions maybe stored, are included herein.

In accordance with various embodiments or aspects, the methods describedherein may be implemented as one or more software programs running on acomputer processor. Dedicated hardware implementations including, butnot limited to, application specific integrated circuits, programmablelogic arrays, and other hardware devices can likewise be constructed toimplement the methods described herein. Furthermore, alternativesoftware implementations including, but not limited to, distributedprocessing or component/object distributed processing, parallelprocessing, or virtual machine processing can also be constructed toimplement the methods described herein.

It should also be noted that software that implements the disclosedmethods may optionally be stored on a tangible storage medium, such as:a magnetic medium, such as a disk or tape; a magneto-optical or opticalmedium, such as a disk; or a solid state medium, such as a memory cardor other package that houses one or more read-only (non-volatile)memories, random access memories, or other re-writable (volatile)memories. The software may also utilize a signal containing computerinstructions. A digital file attachment to e-mail or otherself-contained information archive or set of archives is considered adistribution medium equivalent to a tangible storage medium.Accordingly, a tangible storage medium or distribution medium as listedherein, and other equivalents and successor media, in which the softwareimplementations herein may be stored, are included herein.

Thus, a system and method of providing contextualized display andcontrol functionality in a secure manner have been described. Althoughspecific example embodiments or aspects have been described, it will beevident that various modifications and changes may be made to theseembodiments or aspects without departing from the broader scope of theinvention. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense. Theaccompanying drawings that form a part hereof, show by way ofillustration, and not of limitation, specific embodiments or aspects inwhich the subject matter may be practiced. The embodiments or aspectsillustrated are described in sufficient detail to enable those skilledin the art to practice the teachings disclosed herein. Other embodimentsor aspects may be utilized and derived therefrom, such that structuraland logical substitutions and changes may be made without departing fromthe scope of this disclosure. This Detailed Description, therefore, isnot to be taken in a limiting sense, and the scope of variousembodiments or aspects is defined only by the appended claims, alongwith the full range of equivalents to which such claims are entitled.

Such embodiments or aspects of the inventive subject matter may bereferred to herein, individually and/or collectively, by the term“invention” merely for convenience and without intending to voluntarilylimit the scope of this application to any single invention or inventiveconcept if more than one is in fact disclosed. Thus, although specificembodiments or aspects have been illustrated and described herein, itshould be appreciated that any arrangement calculated to achieve thesame purpose may be substituted for the specific embodiments or aspectsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments or aspects. Combinations of the aboveembodiments or aspects, and other embodiments or aspects notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

The Abstract is provided to comply with 37 C.F.R. § 1.72(b) and willallow the reader to quickly ascertain the nature and gist of thetechnical disclosure. It is submitted with the understanding that itwill not be used to interpret or limit the scope or meaning of theclaims.

In the foregoing description of the embodiments or aspects, variousfeatures are grouped together in a single embodiment for the purpose ofstreamlining the disclosure. This method of disclosure is not to beinterpreted as reflecting that the claimed embodiments or aspects havemore features than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment or aspect. Thus the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separate example embodiment or aspect. Itis contemplated that various embodiments or aspects described herein canbe combined or grouped in different combinations that are not expresslynoted in the Detailed Description. Moreover, it is further contemplatedthat claims covering such different combinations can similarly stand ontheir own as separate example embodiments or aspects, which can beincorporated into the Detailed Description.

The invention claimed is:
 1. A method of interacting with a vehicle, themethod comprising: determining, by a mobile computing device, a positionof the mobile computing device with respect to a component of aplurality of components of the vehicle, the position identifying thecomponent distinct from other components of the plurality of components;obtaining, by the mobile computing device, a context associated with auser input in relation to the component of the vehicle, the contextbased at least on the position of the mobile computing device withrespect to the component of the vehicle as identified; generating, bythe mobile computing device, an instruction based on the user input andthe context; transmitting, by the mobile computing device, theinstruction to the vehicle to generate a control or indication inconnection with the component of the vehicle based on the instruction;applying, by a vehicle subsystem, the control to the component of thevehicle; and indicating, by the mobile computing device, anacknowledgement or a result associated with the instruction to thevehicle.
 2. The method of claim 1, wherein the method further comprisesreceiving the user input.
 3. The method of claim 1, wherein the userinput is one of a biometric input, an audio input, a video input, abutton input, a button sequence input, a code input, and one or morecombinations.
 4. The method of claim 1, wherein the method furthercomprises selecting the context from one or more contexts obtained fromat least one of the mobile computing device, the vehicle, a serviceprovider, and a home control system.
 5. The method of claim 1, whereinthe instruction is a command to control the component of the vehicle. 6.The method of claim 5, wherein the method further comprises generatingan indication of the command, the indication comprising one of video,audio, actuation, and one or more combinations.
 7. The method of claim1, wherein the method further comprises obtaining an initiationindicator.
 8. The method of claim 7, wherein the initiation indicator isone of a user indicator and a system indicator.
 9. The method of claim7, wherein the initiation indicator comprises the context.
 10. Themethod of claim 7, wherein obtaining the initiation indicator comprises:detecting whether there is an anomaly in at least one of user activityand vehicle activity; and generating the initiation indicator when theanomaly is detected.
 11. The method of claim 1, wherein the methodfurther comprises receiving the result associated with the instruction.12. The method of claim 11, wherein the method further comprisesgenerating an indication of the result by the mobile computing device,the indication comprising one of video, audio, actuation, and one ormore combinations.
 13. The method of claim 12, wherein the methodfurther comprises: determining whether the result is in indicatableformat; and obtaining the result in indicatable format when the resultwas not in indictable format.
 14. The method of claim 1, wherein themethod further comprises: generating a dual security association basedon association of user credentials and mobile computing devicecredentials; generating a triple security association based on the dualsecurity association and one of service provider credentials and vehiclecredentials; and forming a communication session based on the triplesecurity association.
 15. A system to interact with a vehicle, thesystem comprising: a mobile computing device comprising: a processingdevice; and a memory device to store instructions that, when executed bythe processing device, cause the processing device to perform operationscomprising: determining a position of the mobile computing device withrespect to a component of a plurality of components of the vehicle, theposition identifying the component distinct from other components of theplurality of components; obtaining a context associated with a userinput in relation to the component of the vehicle, the context based atleast on the position of the mobile computing device with respect to thecomponent of the vehicle as identified; generating an instruction basedon the user input and the context; and transmitting the instruction tothe vehicle to generate a control or indication in connection with thecomponent of the vehicle based on the instruction; and a vehiclesubsystem configured to apply the control or indication to the componentof the vehicle, wherein the operations further comprise indicating bythe mobile computing device an acknowledgment or a result associatedwith the instruction to the vehicle.
 16. The system of claim 15, whereinthe operations further comprise receiving the user input.
 17. The systemof claim 15, wherein the user input is one of a biometric input, anaudio input, a video input, a button input, a button sequence input, acode input, and one or more combinations.
 18. The system of claim 15,wherein the operations further comprise selecting the context from oneor more contexts obtained from at least one of the mobile computingdevice, the vehicle, a service provider, and a home control system. 19.The system of claim 15, wherein the instruction is a command to controlthe component of the vehicle.
 20. The system of claim 19, wherein theoperations further comprise generating an indication of the command, theindication comprising one of video, audio, actuation, and one or morecombinations.
 21. The system of claim 15, wherein the operations furthercomprise obtaining an initiation indicator.
 22. The system of claim 21,wherein the initiation indicator is one of a user indicator and a systemindicator.
 23. The system of claim 21, wherein the initiation indicatorcomprises the context.
 24. The system of claim 21, wherein theoperations further comprise: detecting whether there is an anomaly in atleast one of user activity and vehicle activity; and generating theinitiation indicator when the anomaly is detected.
 25. The system ofclaim 15, wherein the operations further comprise receiving the resultassociated with the instruction.
 26. The system of claim 25, wherein theoperations further comprise generating an indication of the result bythe mobile computing device, the indication comprising one of video,audio, actuation, and one or more combinations.
 27. The system of claim26, wherein the operations further comprise: determining whether theresult is in indicatable format; and obtaining the result in indicatableformat when the result was not in indictable format.
 28. The system ofclaim 26, wherein the operations further comprise: generating a dualsecurity association based on association of user credentials and mobilecomputing device credentials; generating a triple security associationbased on the dual security association and one of service providercredentials and vehicle credentials; and forming a communication sessionbased on the triple security association.